Supporting different instruction set architectures during run time

ABSTRACT

A platform may use heterogeneous instruction set architectures which may be called during run time. Using a system table, an operating system may be directed to the appropriate services for any of two or more instruction set architectures during run time.

BACKGROUND

This invention relates generally to firmware for processor-based systems.

Processor-based systems may use firmware for booting an operating system. Generally, firmware initiates a system using a particular instruction set architecture. For example, a 32 bit Pentium® architecture platform boots in a flat model protected mode using 32 bit callable interfaces in a 4 gigabyte address space.

After booting, the operating system takes control during a stage called run time. The run time system still uses the same instruction set architecture. However, newer systems can support 32 bit or 64 bit instruction set architectures during run time. A number of other instruction set architectures are also available.

An operating system that was booted in a particular 32 bit instruction set architecture has no support for calling back into the 32 bit mode from the kernel during run time. This problem is addressed by one manufacturer by simply prohibiting the kernel from calling back from one instruction set architecture into another instruction set architecture. See BIOS and Kernel Developer's Guide for AMD Athalon™ 64 and AMD Opteron Processors, Publication No. 26094, Revision 306, dated September 2003, available from Advanced Micro Devices, Inc., Sunnyvale, Calif. While this certainly overcomes the problem, it does so in a relatively inflexible way.

Thus, there is a need for ways to enable call backs by an operating system kernel to an instruction set architecture different from the one used to boot the system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic depiction of a platform in accordance with one embodiment of the present invention;

FIG. 2 is a schematic depiction of a software stack using an extensible firmware interface in accordance with one embodiment of the present invention;

FIG. 3 is a schematic depiction of a firmware table in accordance with one embodiment of the present invention; and

FIG. 4 is a flow chart for software in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION

Referring to FIG. 1, a platform or processor-based system 10 may include a processor 12 coupled by a bus 14 to system memory 18 and a firmware storage 16. The firmware storage 16 may store the firmware for executing the boot sequence and the power on self-test. The firmware 16 may be a basic input/output system and it may include an extensible firmware interface application program interface in some embodiments of the present invention.

In order to boot an operating system, the firmware stored in the firmware storage 16 is loaded into system memory 18 and executed to configure the system 10 in a given instruction set architecture. The given instruction set architecture may be preset by the firmware stored in the storage 16. Available instruction set architectures include 32 bit instruction set architecture such as real-mode legacy basic input/output system, protected mode extensible firmware interface, and 64 bit instruction set architectures available from various manufacturers.

Referring to FIG. 2, a system stack for an extensible firmware interface embodiment is illustrated. The extensible firmware interface application program interface 34 has an element that is accessible by the operating system 40 and also has elements accessible by the extensible firmware interface operating system loader and extensible firmware interface boot services. The extensible firmware interface boot services may include drivers, boot devices, protocols, and handlers, as well as timer and memory functions. Thus, an extensible firmware interface embodiment may be implemented which is accessible by the operating system 40.

A legacy operating system loader 42 may conventionally be included, as well as various extensible firmware interface run time services 32. The platform's specific firmware, such as the basic input/output system (BIOS) and system abstraction layer (SAL) 28, may be provided over platform or system 10 hardware. The platform hardware 10 may include a memory partition for the operating system 24 and a partition for the extensible firmware interface system 26. That partition may also include an operating system loader 22 in one embodiment of the present invention.

Referring to FIG. 3, a region of system memory 18 of four gigabytes may be established initially in one embodiment. That memory region may store a configuration table 54 and a system table 56. The system table 56 may include its own configuration table 60. The configuration table 60 may have globally unique identifiers (GUIDs). For example, referring to the GUID/Pointer pair list 62 from the table 60, the GUIDs 1 and 2 are coupled to a pointer 1 and a pointer 2. The pointer 2 may interface to an Advanced Configuration and Power Interface Specification (ACPI) 2.0 table 64. See ACPI Specification Rev. 2.0, available from Microsoft Corporation, Redmond, Wash. 98052-6399. The GUID 3 may be unused in one embodiment or may be used to specify the boot instruction set architecture in one embodiment.

The GUID 4 uses a pointer 4 to point to a system table pointer 66. The system table pointer 66 implements a 64 bit instruction set architecture in one embodiment of the present invention. Also stored in the memory 18 may be 64 bit extensible firmware interface run time drivers 58 in one embodiment.

Because the extensible firmware interface application program interface 34 provides an entry point that is accessible by the operating system 40, it is callable at any time by the operating system. A kernel can call the extensible firmware interface firmware services 32 from the kernel in the mode in which the processor 12 was originally booted.

The system table 62 includes a pointer to an instruction set system table 66 for handling a different instruction set than the one in which the system booted, such as a 64 bit instruction set architecture. The system table 56 gets handed off to the operating system loader 38 and it looks in the system table 56 to find, for example, the ACPI 2.0 table 64 or the System Management (SM) BIOS tables (not shown in FIG. 3). The ACPI table 64 is used to configure interrupt routing and the number of processors.

The GUID 4 provides a set of run time services that are 64 bit callable in one embodiment of the present invention. However, the GUID 4 can also be used to provide services associated with any instruction set architecture other than the one in which the system booted in.

At this point, through the use of the system table 56, both instruction set architectures have their own associated bits of code that may be called by the operating system. Then, when the operating system goes into a different mode, such as the 64 bit mode, it can discover the new set of run time services (for example that are 64 bit friendly), using the system table 56.

The operating system's kernel may go into the system table 56 and look for the GUID 4. In one embodiment, the GUID 4 is 128 bit value that defines 64 bit callable run time services. The GUID 3, in one embodiment, may be a 128 bit value to specify the current instruction set architecture.

Referring to FIG. 4, the software for implementing one embodiment of the present invention begins with a system restart as indicated in block 68. Memory, networking, input/output, and system parameters may be initialized, as indicated in block 70, as part of the boot process. In one embodiment, an EFI services and system table 56 for the native instruction set architecture may be installed as indicated in block 72. The native instruction set architecture is the one used during the boot process. A check at diamond 74 determines whether any additional drivers need to be loaded. If so, those drivers are loaded as indicated in block 76.

A check at diamond 78 determines whether the platform may support an additional instruction set architecture. If so, the configuration table pointer in block 62 is installed to the new instruction set architecture services as indicated in block 80.

A check at diamond 82 determines whether there is any locally installed instruction set architecture. If not, a pre-boot execution environment (PXE) boot operating system may be booted. If so, a locally installed operating system may be booted as indicated in block 86.

Next, a system table is obtained as part of the operating system handoff. An exit boot services command may be issued as indicated in block 88. In diamond 90, a determination is made as to whether, at any time after boot during run time, the operating system wishes to change mode. The mode change can be any change from one instruction set architecture to another. A typical change may be to change from a 32 bit mode to a 64 bit or long mode. If no such operating system change is detected in diamond 90, execution of the operation system kernel recommences as indicated in block 94. If an instruction set architecture change is detected, the operating system transitions to the new instruction set architecture such as the long mode as indicated in block 92.

Execution of the operating system kernel continues with determining whether the operating system kernel needs to invoke some run time service as indicated in diamond 96. If not, execution can continue. But if a run time service is needed, especially in the new instruction set architecture as determined in diamond 96, a check at diamond 98 determines whether the operating system has transitioned from the originally booted instruction set architecture. If so, a check at diamond 102 determines whether the new instruction set architecture GUID is provided in the original system table 56 GUID/pointer pair list 62. If so, the associated service, such as the pointer 66, may be called through the instruction set architecture system table's run time services 66. If there is no such entry in the list 62, an error may be returned to the caller.

Thus, in accordance with some embodiments of the present invention, heterogeneous instruction set architectures may be called during run time. For example, this ability of the kernel to call different instruction set architectures during run time permits the operating system kernel to call services that are not available with the instruction set architecture used to originally boot the system.

While the present invention has been described with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present invention. 

1. A method comprising: enabling an operating system kernel in a platform to invoke services that are not available with the instruction set architecture used to boot the platform.
 2. The method of claim 1 including establishing a table that links an identifier with a pointer for an instruction set architecture different from the one used to boot the platform.
 3. The method of claim 1 including linking to a table which also identifies the instruction set architecture used to boot the platform.
 4. The method of claim 1 including enabling an operating system kernel booted in a 32 bit instruction set architecture to call services associated with a 64 bit instruction set architecture.
 5. The method of claim 1 including establishing a configuration table that links globally unique identifiers with pointers associated with an instruction set architecture different from the instruction set architecture used to boot the platform.
 6. The method of claim 1 including enabling an operating system during run time to access run time services for two different instruction set architectures.
 7. The method of claim 6 including using an extensible firmware interface service to access two different instruction set architectures.
 8. The method of claim 1 including associating an instruction set architecture with a globally unique identifier during a boot stage.
 9. The method of claim 8 including consulting a table during run time to locate services for different instruction set architectures.
 10. The method of claim 1 including enabling an operating system to access an application program interface of an extensible firmware interface during run time to locate instruction set architecture services for two different instruction set architectures.
 11. An article comprising a medium storing instructions that, if executed, enable a platform to allow an operating system kernel to invoke services that are not available with the instruction set architecture used to boot the platform.
 12. The article of claim 11 further storing instructions that, if executed, enable the platform to establish a table that links an identifier with a pointer for an instruction set architecture different from the one used to boot the platform.
 13. The article of claim 11 further storing instructions that, if executed, enable the platform to link to a table which also identifies the instruction set architecture used to boot the platform.
 14. The article of claim 11 further storing instructions that, if executed, enable the platform operating system kernel booted in a 32 bit instruction set architecture to call the services associated with a 64 bit instruction set architecture.
 15. The article of claim 11 further storing instructions that, if executed, enable the platform to establish a configuration table that links globally unique identifiers with pointers associated with an instruction set architecture different from the instruction set architecture used to boot the platform.
 16. The article of claim 11 further storing instructions that, if executed, enable the platform to allow the operating system to access run time services for two different instruction set architectures.
 17. The article of claim 16 further storing instructions that, if executed, enable the platform to use an extensible firmware interface service to access two different instruction set architectures.
 18. The article of claim 11 further storing instructions that, if executed, enable the platform to associate an instruction set architecture with a globally unique identifier during a boot stage.
 19. The article of claim 18 further storing instructions that, if executed, enable the platform to consult a table during run time to locate services for different instruction set architectures.
 20. The article of claim 11 further storing instructions that, if executed, enable the platform to access an application program interface of an extensible firmware interface during run time to locate instruction set architecture services for two different instruction set architectures.
 21. A platform comprising: a processor; and a storage storing instructions that, if executed, enable an operating system kernel in the platform to invoke services that are not available with the instruction set architecture used to boot the platform.
 22. The platform of claim 21 wherein said storage stores instructions that, if executed, enable the platform to establish a table that links an identifier with a pointer for an instruction set architecture different from the one used to boot the platform.
 23. The platform of claim 21 wherein said storage stores instructions that, if executed, enable the platform to link to a table that also identifies the instruction set architecture used to boot the platform.
 24. The platform of claim 21 wherein said storage further stores instructions that, if executed, enable the platform operating system kernel booted in a 32 bit instruction set architecture to call the services associated with a 64 bit instruction set architecture.
 25. The platform of claim 21 wherein said storage stores instructions that, if executed, enable the platform to establish a configuration table that links globally unique identifiers with pointers associated with an instruction set architecture different from the instruction set architecture used to boot the platform.
 26. The platform of claim 21 wherein said storage stores instructions that, if executed, enable the platform to allow the operating system to access run time services for two different instruction set architectures.
 27. The platform of claim 26 wherein said storage stores instructions that, if executed, enable the platform to use an extensible firmware interface service to access two different instruction set architectures.
 28. The platform of claim 21 wherein said storage stores instructions that, if executed, enable the platform to associate instruction set architecture with a globally unique identifier during a boot stage.
 29. The platform of claim 28 wherein said storage stores instructions that, if executed, enable the platform to consult a table during run time to locate services for different instruction set architectures.
 30. The platform of claim 21 wherein said storage stores instructions that, if executed, enable the platform to access an application program interface of an extensible firmware interface during run time to locate instruction set architecture services for two different instruction set architectures. 